Learn how to configure your Personalization strategy using the Algolia dashboard.
Select events
Add events
Set weights
Simulate
Tweak events and weights
X
button to the right of an event’s weight.Configure facets
Save
attributesForFaceting
so that users can filter on them in the UI
That doesn’t mean you should include them all in the Personalization strategy.
Of these attributes, genre and author are probably the best indicators of a user’s affinities, while publisher, and stock status may be the least.
Users tend to prefer certain authors, but they probably pay less attention to the publisher.
The publish date can distinguish users that prefer newer books versus those who prefer older editions or don’t have a preference.
In summary, you can rank the facets like this:
attributesForFaceting
.attributesForFaceting
.
For example, suppose you have a categories
attribute, with different nested categories:
categories.genres
or categories.similar_artists
as facets for Personalization, you need to explicitly declare them, and not just categories
, as attributesForFaceting
.
Once you’ve declared all desired attributes as attributesForFaceting
, weighting facets is similar to weighting events.
Select facets
Add facets
attributesForFaceting
.Set weights
Simulate
Tweak facets and weights
X
button to the right of a facet’s weight.Configure events
Save
customRanking
.
Select Personalization impact
Set impact
Simulate
A. Position of the result
-
.↗
arrow.↘
arrow↗
arrow without the number of positions the result moved.1.
(the absolute position), the simulator displays ↗ 1
to indicate it moved up one position due to Personalization.B. Personalization effect
C. Facet value affinities
type:book
and categories:historical
.
The user has shown an affinity for these values through earlier behavior included in the Personalization strategy as events.
For example, they may have previously clicked on or bought an item with these facet values.
The result just below it has type:book
and categories:contemporary
. Since categories:historical
has an affinity score of 17 and categories:contemporary
has an affinity score of 14, the historical book was boosted to the first position, though they have the same textual and business relevance.
Algolia computes these affinity scores using the events, facets, and respective weights you’ve included in your strategy.
For example, the user may have added a contemporary book to their shopping cart but never actually bought it, while they did buy a book abour history.
Assuming you’ve set a lower weight for the “Add product to cart” event than the “Buy product” event, this explains the lower affinity score for categories:contemporary
as compared to categories:historical
.
Accordingly, given the same textual relevance, Algolia boosts results with categories:historical
over results with categories:contemporary
.
Select the Simulator
Select the user
Optional: enter a search query
Select an index
Select attributes
Compare results
Repeat
Adjust strategy
Save